We can just install the electron-builder and add the scripts to the "electron" test folder. That way we don't need to maintain two equal html and js files.

Let me suggest an alternative layout. In addition to test/electron, there could be an examples/electron folder, where the package.json file refers to "steamworks.js": "latest" rather than ../...

As I'm imagining it, goal of the examples is to be dead simple, requiring end users to do as little as possible to get started with steamworks.js.

So, there would be examples/electron/electron-builder, examples/electron/electron-forge, and examples/electron/electron-packager. Since the goal of the examples is to be simple, having extra copies of the html and js would be fine/expected.

WDYT?

Sounds good, would be nice to add this example too: https://github.com/ceifa/steamworks.js-microtransaction-example

These examples were helpful for me. I've been struggling to use steamworks.js and these helped. Thank you for adding them!

Is it possible to add an example where we can listen to events from the steam client? Specifically I need to detect when the Steam Overlay opens and closes.

Is it possible to add an example where we can listen to events from the steam client? Specifically I need to detect when the Steam Overlay opens and closes.

This callback is not implemented on the steamworks.js API yet